home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / p_man / cat3 / sat_intrp_pathname.z / sat_intrp_pathname
Text File  |  1998-10-20  |  7KB  |  133 lines

  1.  
  2.  
  3.  
  4. SSSSAAAATTTT____IIIINNNNTTTTRRRRPPPP____PPPPAAAATTTTHHHHNNNNAAAAMMMMEEEE((((3333))))                                    SSSSAAAATTTT____IIIINNNNTTTTRRRRPPPP____PPPPAAAATTTTHHHHNNNNAAAAMMMMEEEE((((3333))))
  5.  
  6.  
  7.  
  8. NNNNAAAAMMMMEEEE
  9.      ssssaaaatttt____iiiinnnnttttrrrrpppp____ppppaaaatttthhhhnnnnaaaammmmeeee - Portable interface to interpret sat_pathname
  10.      structs.
  11.  
  12. SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.      ####iiiinnnncccclllluuuuddddeeee <<<<ssssaaaatttt....hhhh>>>>
  14.  
  15.      iiiinnnntttt ssssaaaatttt____iiiinnnnttttrrrrpppp____ppppaaaatttthhhhnnnnaaaammmmeeee ((((cccchhhhaaaarrrr ********bbbbuuuuffff,,,, ssssttttrrrruuuucccctttt ssssaaaatttt____ppppaaaatttthhhhnnnnaaaammmmeeee ****ppppnnnn,,,, cccchhhhaaaarrrr
  16.           ********rrrreeeeqqqqnnnnaaaammmmeeee,,,, cccchhhhaaaarrrr ********aaaaccccttttnnnnaaaammmmeeee,,,, mmmmaaaacccc____llllaaaabbbbeeeellll ********llllaaaabbbbeeeellll,,,, iiiinnnntttt ffffiiiilllleeee____mmmmaaaajjjjoooorrrr,,,, iiiinnnntttt
  17.           ffffiiiilllleeee____mmmmiiiinnnnoooorrrr))));;;;
  18.  
  19. DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  20.      ssssaaaatttt____iiiinnnnttttrrrrpppp____ppppaaaatttthhhhnnnnaaaammmmeeee takes a pointer to a buffer (_b_u_f) containing the disk
  21.      image of a ssssaaaatttt____ppppaaaatttthhhhnnnnaaaammmmeeee structure.  It unpacks the variable length
  22.      portions of the struct from _b_u_f and returns them in the specified
  23.      arguments.  A pointer to the data following the pathname information is
  24.      returned in _b_u_f.
  25.  
  26.      The ssssaaaatttt____ppppaaaatttthhhhnnnnaaaammmmeeee structure includes the following fields:
  27.  
  28.           iiiinnnnoooo____tttt   ssssaaaatttt____iiiinnnnooooddddeeee;;;;       ////**** iiiinnnnooooddddeeee nnnnuuuummmmbbbbeeeerrrr ooooffff ffffiiiilllleeee ****////
  29.           ddddeeeevvvv____tttt   ssssaaaatttt____ddddeeeevvvviiiicccceeee;;;;      ////**** ddddeeeevvvviiiicccceeee nnnnoooo.... ooooffff mmmmoooouuuunnnntttteeeedddd ffffiiiilllleeee ssssyyyysssstttteeeemmmm ****////
  30.           uuuuiiiidddd____tttt   ssssaaaatttt____ffffiiiilllleeeeoooowwwwnnnn;;;;     ////**** ffffiiiilllleeee oooowwwwnnnneeeerrrr ****////
  31.           ggggiiiidddd____tttt   ssssaaaatttt____ffffiiiilllleeeeggggrrrrpppp;;;;     ////**** ffffiiiilllleeee ggggrrrroooouuuupppp ****////
  32.           mmmmooooddddeeee____tttt  ssssaaaatttt____ffffiiiilllleeeemmmmooooddddeeee;;;;    ////**** ffffiiiilllleeee mmmmooooddddeeee,,,, iiiinnnncccclllluuuuddddiiiinnnngggg ffffiiiilllleeee ttttyyyyppppeeee ****////
  33.  
  34.      Additional data is appended to the struct in the disk format.  This
  35.      informtaion is returned in the arguments as follows:
  36.  
  37.      _r_e_q_n_a_m_e        The pathname that the system call specified
  38.  
  39.      _a_c_t_n_a_m_e        The pathname that the the system actually looked up,
  40.                     including crossed mount points, symbolic links, and
  41.                     multi-level directories.
  42.  
  43.      _l_a_b_e_l          The security label of the file.  It is preferred, but not
  44.                     required, to only specify this field if ssssaaaatttt____mmmmaaaacccc____eeeennnnaaaabbbblllleeeedddd is
  45.                     set in the file header.
  46.  
  47.      If any of these fields are NULL, the related information will not be
  48.      returned.  If these fields are non-null (i.e. they represent the address
  49.      of a suitable pointer), sufficient storage will be allocated to hold the
  50.      values.  These fields should be freed (see ffffrrrreeeeeeee(3)) when they are no
  51.      longer needed.
  52.  
  53.      The file label is only available if ssssaaaatttt____mmmmaaaacccc____eeeennnnaaaabbbblllleeeedddd is set in the file
  54.      header, otherwise this field will be NULL.  To avoid possible problems if
  55.      trailing data happens to resemble a mmmmaaaacccc____llllaaaabbbbeeeellll, do not ask for the file
  56.      label unless ssssaaaatttt____mmmmaaaacccc____eeeennnnaaaabbbblllleeeedddd is set in the file header.
  57.  
  58.  
  59.  
  60.  
  61.  
  62.  
  63.                                                                         PPPPaaaaggggeeee 1111
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70. SSSSAAAATTTT____IIIINNNNTTTTRRRRPPPP____PPPPAAAATTTTHHHHNNNNAAAAMMMMEEEE((((3333))))                                    SSSSAAAATTTT____IIIINNNNTTTTRRRRPPPP____PPPPAAAATTTTHHHHNNNNAAAAMMMMEEEE((((3333))))
  71.  
  72.  
  73.  
  74. DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
  75.      ssssaaaatttt____rrrreeeeaaaadddd____hhhheeeeaaaaddddeeeerrrr____iiiinnnnffffoooo returns 0 on success or -1 if the ssssaaaatttt____ppppaaaatttthhhhnnnnaaaammmmeeee
  76.      struct is not valid.  In this case, an error message is displayed on
  77.      stderr.
  78.  
  79. SSSSEEEEEEEE AAAALLLLSSSSOOOO
  80.      ffffrrrreeeeeeee(3C), ssssaaaatttt____rrrreeeeaaaadddd____ffffiiiilllleeee____iiiinnnnffffoooo(3), ssssaaaatttt____rrrreeeeaaaadddd____hhhheeeeaaaaddddeeeerrrr____iiiinnnnffffoooo(3).
  81.  
  82.  
  83.  
  84.  
  85.  
  86.  
  87.  
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.                                                                         PPPPaaaaggggeeee 2222
  130.  
  131.  
  132.  
  133.